upgrade hydrator 2.0#777
Conversation
|
Hello 👋 here is the most recent benchmark result:
This comment gets update everytime a new commit comes in! |
|
This could also land in 3.x, no? |
da48f2e to
3ad383c
Compare
c8bf73c to
432a747
Compare
2b345c4 to
b82ed3c
Compare
|
Ok, now this cannot land anymore in 3.x |
|
I would first look at what the optimal version for 4.x would look like and then see if it can be implemented in 3.x. |
73842e6 to
d3ce7a5
Compare
9a1ead6 to
8c81f2b
Compare
8c81f2b to
ece40e4
Compare
| #[Processor('delete_personal_data')] | ||
| final class DeletePersonalDataProcessor | ||
| final class DeleteSensitiveDataProcessor |
|
|
||
| Renaming an event through an upcaster is no longer supported, because the event class is | ||
| already resolved from the stored event name before the payload is upcasted. | ||
| Use [event aliases](events.md#alias) instead. |
There was a problem hiding this comment.
Renaming an event through an upcaster is no longer supported,
This phrasing is better suited in the upgrade docs. Here in the actual 4.x docs, we should not say that its is no longer supported. Instead we should hint the user how he could solve it and link to the right direction. So I think a note how to get rid of old event names form the store should be added, if we keep this section here: recreate the store (which even does not need any translator)
|
|
||
| :::danger | ||
| The key table layout changed (`crypto_keys` -> `cryptography_keys` with new columns). | ||
| Existing keys must be migrated, otherwise stored sensitive data can no longer be decrypted. |
There was a problem hiding this comment.
We should add a note how to migrate
No description provided.